In the standard lay-out, an EAN number (barcode) field is added with which the assortment barcode is printed on the stock label. This field can be added in existing label layouts, for more information read the manual. After adding the field, the font must still be adjusted.

When creating a wish list, other photos in the list can be manually linked than indicated via the WinTree settings. The selected photos in the list are now also sent when the list is sent to customers via TreeCommerce Messenger.

Update your wish list automatically and send it via TreeCommerce Messenger every night? This is now possible. TSD can create a task in the WinTree database which automatically refreshes certain wish-lists and then sends them to a selection of TCM members. Please contact TSD if this task needs to be set-up in WinTree.

The document personalized wish list (document 370) is now available for all WinTree users. This document can be used to send a wish list to (a selection of) customers with the address printed on the document. Before printing or e-mailing this document, please check in File -> Settings -> Lists -> Print group Find/ Wish list that the Show and E-mail option is selected. If that is the case, the document can be used from the menu Assortment -> Maintenance Search/ Wish list via the Print and E-mail button.

If a sales order is placed in a work order using the [Direkt] button, the App colour and optionally the time can now also be set in the pop-up screen.

An allocation text can be entered when splitting a sales line. When a sales line is split with an allocation text, this text is also stored in the splitted sales line.
Contact TSD if this is required.

Based on a delivery, a Delivery Header Label (document 415) can be printed. This label is converted to a FastReport document so that changes and additions of fields in the layout can be made easily (by TSD). Please contact TSD if the current layout of this label needs to be changed.

When using the Trade units module, the required packaging can be converted when creating a delivery. This information can now also be included in a custom report for the Picking List.
Please contact TSD if the current Picking List report needs to be adapted for this purpose. TSD will schedule the work to create a user report.

In the lay-out of a fore run label, to be printed at the same time as a lifting label, the contents of the field Characteristic 2 (where the location description or a supplier name used to be) has been adjusted. If the batches are present (status = 0), the location description is printed. If the batches have been purchased and not yet received (status = 1), the supplier name is printed. If the batches have been purchased, called-up but not yet received (status = 2), the text On the way/supplier name is printed in the field.

Article codes must also be printed with the fore run number zero on the CMR. Without a fore run number these codes are no longer accepted in GB since the Brexit. So e.g. 06029048 instead of 6029048.

A new report is available in the delivery print screen: 445 Commercial Invoice. This document, also called a commercial invoice or trade invoice, is a special export document that helps your package through customs. A properly completed commercial invoice for export helps customs authorities quickly decide which taxes and import duties apply to your package. In addition, custom officials can see whether your parcel meets all requirements and can pass on the information to the destination country (e.g. which tax obligations the recipient has). This form is only needed for parcels outside the EU. This document is only available if module 139: Export outside EU is active.

When printing a delivery label, passport field C is by default filled with the delivery number. Using parameter 2617 (value = 2) passport field C can now also be filled with the batch number of the allocated batch. If the delivery is divided into several batches, the batch number of the first batch that is classified will be printed. If the delivery is not classified, the delivery number will still be printed.

If a delivery label for lifting/call-ups is printed with passport data, passport field C is by default filled with the batch number of the allocated batch. However, it is possible that the label is printed based on allocated batches which still have the status "At Supplier" or "On the way". In that case, the batch number of the allocated batch is different from the batch number of the allocation which has been received. As a result, it can happen that the passport field C on labels has a different number than the passport data which can be printed on a shipping list and/or sales invoice.
 
To prevent this, parameter 2617 is available. If this work order is set to value 1, the passport field C will be filled everywhere with the delivery number when printing (labels and lists). The default value for this parameter is 0. This causes passport field C to be filled with the batch number of the allocated batch.

When the extended function for collection areas is used in WinTree, an extra function can be activated to link delivery conditions to a certain (series of) collection areas, through parameter 2616 (to be set by TSD). When a delivery has a certain condition then only the collection areas, linked to that delivery, can be selected.

Due to the Brexit, exporters to England need purchase lines from their suppliers that meet certain requirements. With an additional selection possibility in the call-up screen on the country from the customer's delivery address, all lines to be called-up for UK customers can be shown in the screen. This allows (collective) header or footer texts with additional information to be sent to the supplier.

If a stock batch was originally purchased on its own location, the original supplier remains linked to the batch. It can happen that stock batches are manually booked on a location (original supplier cannot be determined by WinTree). By setting parameter 2629 it is still possible to link a supplier number to these stock batches. This way it is always possible to trace where the stock came from. If a stock batch is placed on a location via a purchase order, then the existing supplier number cannot be changed.

In the modules Scanning of Incoming and Outgoing Goods, an option is present to print retail labels for customers immediately upon receipt of goods. Now it can happen that for certain articles retail labels do not need to be printed, while for other articles that are received at that time, retail labels should be printed.
To regulate this, a new parameter 2619, to be set by TSD, is available. If this parameter has value 1, only the retail labels of those articles with a retail price > 0 will be printed. All articles for which the retail price is 0 will not be printed. In this way you can set per item/per customer for which items retail labels should or should not be printed.

If goods are received via the scan function Goods Inward, the separately scanned lines are counted by item for checking purchase invoices. This results in fewer lines when checking the purchase invoices.

In the genus groups, a 5th planttype has been added: Woody plants, bulbs (12 months). This function ensures that 12 months after the including date, this consignment becomes the phytosanitary country of origin instead of the country of origin. This is in contrast to the type of plant: Woody plants, bulbs (growing season) which looks at the date entered.

Printing photos on labels where the photos are stored 'in the cloud' is now also possible. Please contact TSD when photos need to be printed on labels (e.g. for retail or Cash & Carry labels).

When an IBAN number of a supplier is changed in WinTree, the administrator of WinTree will always get a message onscreen when starting WinTree®. This control is built in to prevent fraud through WinTree Financial by abusing IBAN numbers. After closing the message, the user can continue working in WinTree. When WinTree is started up by a user who is not an administrator, the check for adjusted IBAN numbers also takes place, but this is not shown by means of a message in the screen. In both cases an e-mail will be sent to the support department of TSD. An employee of this department will then contact the administrator of WinTree to discuss the reason for changing the IBAN number. In most cases it concerns a legitimate change and no further action is required from the administrator. If the modification of the IBAN number is done by a WinTree user and he/she cannot give a clear reason for this, the administrator of WinTree can discuss this further with this employee. TSD has no further role in this.

When transferring batches, parameter 104 can be used to determine whether batches should be counted together. This counting function has been enhanced to prevent two or more batches of the same article, but from a different supplier, from being added together. This means that batches from different suppliers will never be counted together.

Merge fields can be used in text blocks. If, for example, employee A printed or mailed an order confirmation and his name was placed in a merge field in a text block, the name of the first employee would be displayed when reprinted. Even though the reprint was done by another employee. This has now been changed. When printing or reprinting documents, the correct employee is now always placed in a merge field. As a result, the text blocks no longer show who, for example, has already printed or sent an order by e-mail. The merge field for the employee name remains visible as a code and no longer mentions the name of the first employee.

When creating a free document / proforma, there is a choice of which headers and footers to use. Via parameter 2630, it can be indicated how the preferred choice for the texts must be filled in by default. On Order (=0) or on Invoice (=1) texts. Default is on Order.

Every employee in WinTree can set his own password. It is now possible for the administrator of WinTree to indicate how long a password of an employee remains valid.

Via File-> Settings -> Properties tab a number of options are available for this.

• Checkbox "Possibility to save password at login"; here you can indicate whether an employee has the option to save the entered password at the login screen.
• Checkbox "In case of change, also apply to history databases?"; this allows an adjusted user password to also be adjusted in all available history databases. Please note that this is only done in those history databases in which the user is included in the employee table.
• Dropdown list 'Passwords expire after:'; the following choices are available: infinitely valid, one month, two months, one quarter, six months and one year (value is stored in parameter 2611). A date when the password was last created is stored in the employee table. If the password has expired according to the set expiry date, the employee is notified of this when he logs in and a new password can be set immediately.